Communication Based on Operation Mode

ABSTRACT

Embodiments are provided for utilizing communication routes based operation mode. In an example implementation, while operating in a normal power mode, a playback device maintains information in a network table, the information includes first information associated with a second playback device of the networked media system and second information associated with a third playback device of the networked media system. The playback device determines that the first playback device is to enter a low power mode to draw less power from a battery of the first playback device relative to the normal power mode, and responsive to the determination, foregoing maintaining of the second information in the network table. Thereafter, the playback device determines that the first playback device is to return to normal power mode; and, and in response, synchronizes with the second playback device based at least in part on the first information for playback of audio content.

CROSS REFERENCE TO RELATED APPLICATIONS

This application claims priority under 35 U.S.C. § 120 to, and is acontinuation of, U.S. non-provisional patent application Ser. No.14/994,316, filed on Jan. 13, 2016, entitled “Communication Based OnOperation Mode,” which is incorporated herein by reference in itsentirety. U.S. non-provisional patent application Ser. No. 14/994,316claims priority under 35 U.S.C. § 120 to, and is a continuation of, U.S.non-provisional patent application Ser. No. 14/040,897, filed on Sep.30, 2013, entitled “Communication Routes Based On Low Power Operation,”issued as U.S. Pat. No. 9,298,244 on Mar. 29, 2016, which is alsoincorporated herein by reference in its entirety.

FIELD OF THE DISCLOSURE

The disclosure is related to consumer goods and electronics, personalarea networks (PANs), wireless connectivity protocols, human interfacedevices (HID), personal computer (PC) devices, and, more particularly,to methods, systems, products, features, services, and other itemsdirected to media playback or some aspect thereof.

BACKGROUND

Digital music has become readily available due in part to thedevelopment of consumer level technology that has allowed people tolisten to digital music on a personal audio device. The consumer'sincreasing preference for digital audio has also resulted in theintegration of personal audio devices into PDAs, cellular phones, andother mobile devices. The portability of these mobile devices hasenabled people to take the music listening experience with them andoutside of the home. People have become able to manage or play digitalmusic, like digital music files or even Internet radio, in the homethrough the use of their computer or similar devices. Now there are manydifferent ways to manage or play digital music, in addition to otherdigital content including digital video and photos, stimulated in manyways by high-speed Internet access at home, mobile broadband Internetaccess, and consumer demand for digital media.

Until recently, options for managing and playing digital audio inmultiple different settings were severely limited. In 2005, Sonosoffered for sale its first digital audio system that enabled people to,among many other things, access virtually unlimited sources of audio viaone or more networked connected media players, dynamically group orungroup media players upon command, wirelessly send the audio over alocal network amongst media players, and play the digital audio out loudacross multiple media players in synchrony. The Sonos system can becontrolled by software applications running on network capable mobiledevices and computers.

Given the growing consumer demand for digital media, there continues tobe a need to develop consumer technology that revolutionizes the waypeople access and consume digital media.

BRIEF DESCRIPTION OF THE DRAWINGS

Features, aspects, and advantages of the presently disclosed technologymay be better understood with regard to the following description,appended claims, and accompanying drawings where:

FIG. 1 shows an example configuration in which certain embodiments maybe practiced;

FIG. 2A shows an illustration of an example zone player having abuilt-in amplifier and transducers;

FIG. 2B shows an illustration of an example zone player having abuilt-in amplifier and connected to external speakers;

FIG. 2C shows an illustration of an example zone player connected to anA/V receiver and speakers;

FIG. 3 shows an illustration of an example controller;

FIG. 4 shows an internal functional block diagram of an example zoneplayer;

FIG. 5 shows an internal functional block diagram of an examplecontroller;

FIG. 6 shows an example playback queue configuration for an examplenetwork media system;

FIG. 7 shows an example ad-hoc playback network;

FIG. 8 shows a system including a plurality of networks including acloud-based network and at least one local playback network;

FIG. 9 shows example playback devices and example controllers as part ofan example networked media system;

FIG. 10 shows an example flow diagram for intelligently utilizingcommunication routes based on low power operation;

FIG. 11A shows an illustration of an example bridge table entry;

FIG. 11B shows an illustration of an example bridge table entry based onlow power operation;

FIG. 11C shows an illustration of another example bridge table entry;

FIG. 11D shows an illustration of another example bridge table entrybased on low power operation;

FIG. 12A shows additional example playback devices and an example routeras part of another example networked media system.

FIG. 12B shows an illustration of yet another example bridge tableentry;

FIG. 12C shows an illustration of yet another example bridge table entrybased on low power operation;

In addition, the drawings are for the purpose of illustrating exampleembodiments, but it is understood that this application is not limitedto the arrangements and instrumentality shown in the drawings.

DETAILED DESCRIPTION I. Overview

Embodiments described herein involve communication routes betweenmultimedia playback devices of a networked media system, e.g., a homeentertainment system. In some embodiments, communication routes of thenetworked media system may enable playback devices in a home or“household” to communicate with one another in a mesh network. In otherembodiments, communication routes of the networked media system mayenable playback devices in a home or “household” to communicate with oneanother in a star network, such as through an access point (AP) orrouter. In some instances, a first playback device of a network mediasystem may be configured to communicate with a second playback devicethrough a direct communication route and/or a non-direct communicationroute. For example, the first playback device may be configured toutilize a direct communication route by communicating directly with thesecond playback device. Alternatively, the first playback device may beconfigured to utilize a non-direct communication route. For example, thefirst playback device may send data destined for the second playbackdevice (i.e., the destination device) through a third device (i.e., anintermediary device). In some embodiments, the third device is aplayback device. In other embodiments, the third device is an accesspoint.

In some embodiments, non-direct routing may be beneficial. For example,conventional protocols generally utilize non-direct communication routesto prevent routing loops and/or errors in routing algorithms. However, adrawback to such non-direct routing is the possibility of “triangularrouting.” In some instances, such protocols associated with non-directrouting may cause direct routes to be blocked, whereas direct routes mayprovide a number of advantages as well. For example, considering thescenario above, direct routes may enable the first playback device tobypass indirect forwarding routes through the third device, i.e.,triangular routing, thereby transmitting data straight to the secondplayback device efficiently and with less congestion.

Thus, embodiments described herein may utilize both direct routes andnon-direct routes, in accordance with various types of device modes,e.g., a low power mode. In some instances, a playback device may be abattery-powered device that supports a low power mode. To conservebattery power in such low power modes, the number of direct routes in anetworked media system may be reduced. For example, considering thescenarios above, the first playback device operating in anormal-operating mode may change to a low power device mode. Based onchanging to this low power mode, the first playback device may stopusing direct routes and alternatively utilize non-direct routes tocommunicate with the second playback device. As such, the first playbackdevice may eliminate direct routes with the second playback device andfacilitate its conservation of battery power and energy. In particular,eliminating direct routes may reduce the number of wireless interfacesutilized by the first playback device. In addition, eliminating directroutes may free the first playback device from having to updatecommunication data, e.g., bridge tables, address information, andforwarding tables, among other forms of data.

As indicated above, the present application involves utilizing directand non-direct communication routes based on one or more playbackdevices entering a low power mode. In one aspect, a method is provided.The method involves determining, by a first playback device, that thefirst playback device should enter a low power mode, where the firstplayback device is part of a networked media system. Based on thisdetermination, the method further involves identifying, by the firstplayback device, at least one additional playback device that is part ofthe networked media system, where the first playback device isconfigured to communicate with the at least one additional playbackdevice via (i) a first route, and (ii) a second route. Further, themethod involves informing, by the first playback device, the at leastone additional playback device not to utilize the first route with thefirst playback device. Yet further, the method involves entering, by thefirst playback device, the low power mode. While the first playbackdevice is in the low power mode, the method further involvesperiodically receiving, by the first playback device, a message from amaster device, where the master device is part of the networked mediasystem. Based on the message, the method involves exiting, by the firstplayback device, the low power mode.

In another aspect, a playback device is provided. The playback deviceincludes a processor, a network interface, a non-transitorycomputer-readable storage medium, and program logic stored on thenon-transitory computer-readable medium. The program logic is executableby the processor to determine that the playback device should enter alow power mode, where the playback device is part of a networked mediasystem. Based on the determination, the program logic is furtherexecutable by the processor to identify at least one additional playbackdevice that is part of the networked media system, where the playbackdevice is configured to communicate with the at least one additionalplayback device via (i) a first route, and (ii) a second route. Theprogram logic is further executable by the processor to inform the atleast one additional playback device not to utilize the first route withthe playback device. Yet further, the program logic is executable by theprocessor to enter the low power mode. While the first playback deviceis in the low power mode, the program logic is further executable by theprocessor to periodically receive a message from a master device, wherethe master device is part of the networked media system. Based on themessage, the program logic is further executable by the processor toexit the low power mode.

In yet another aspect, a non-transitory computer-readable storage mediumis provided. The non-transitory computer-readable storage mediumincludes a set of instructions for execution by a processor. The set ofinstructions, when executed, cause a playback device to determine thatthe playback device should enter a low power mode, where the playbackdevice is part of a networked media system. Based on the determination,the set of instructions, when executed, cause the playback device toidentify at least one additional playback device that is part of thenetworked media system, where the playback device is configured tocommunicate with the at least one additional playback device via (i) afirst route, and (ii) a second route. Further, the set of instructions,when executed, cause the playback device to inform the at least oneadditional playback device not to utilize the first route with theplayback device. Further, the set of instructions, when executed, causethe playback device to enter the low power mode. While the firstplayback device is in the low power mode, the set of instructions, whenexecuted, cause the playback device to periodically receive a messagefrom a master device, where the master device is part of the networkedmedia system. Based on the message, the set of instructions, whenexecuted, cause the playback device to exit the low power mode.

Other embodiments, as those discussed in the following and others as canbe appreciated by one having ordinary skill in the art are alsopossible.

II. Example Operating Environment

Referring now to the drawings, in which like numerals can refer to likeparts throughout the figures, FIG. 1 shows an example media systemconfiguration 100 in which one or more embodiments disclosed herein canbe practiced or implemented. It should be noted that media systemconfiguration 100 may also be referred to a networked media systemincluding one or more playback devices, e.g., zone players.

By way of illustration, the media system configuration 100 is associatedwith a home having multiple zones, although it should be understood thatthe home could be configured with only one zone. Additionally, one ormore zones can be added to the configuration 100 over time. Each zonemay be assigned by a user to a different room or space, such as, forexample, an office, bathroom, bedroom, kitchen, dining room, familyroom, home theater room, utility or laundry room, and patio. A singlezone might also include multiple rooms or spaces if so configured. Withrespect to FIG. 1, one or more of zone players 102-124 are shown in eachrespective zone. Zone players 102-124, also referred to herein asplayback devices, multimedia units, speakers, players, and so on,provide audio, video, and/or audiovisual outputs. A controller 130(e.g., shown in the kitchen for purposes of example and explanation)provides control to the media system configuration 100. Controller 130may be fixed to a zone, or alternatively, mobile such that it can bemoved about the zones. The media system configuration 100 may alsoinclude more than one controller 130, and additional controllers may beadded to the system over time.

The media system configuration 100 illustrates an example whole housemedia system, though it is understood that the technology describedherein is not limited to, among other things, its particular place ofapplication or to an expansive system like a whole house media system100 of FIG. 1.

a. Example Zone Players

FIGS. 2A, 2B, and 2C show example types of zone players. Zone players200, 202, and 204 of FIGS. 2A, 2B, and 2C, respectively, can correspondto any of the zone players 102-124 of FIG. 1, for example. In someembodiments, audio is reproduced using only a single zone player, suchas by a full-range player. In some embodiments, audio is reproducedusing two or more zone players, such as by using a combination offull-range players or a combination of full-range and specializedplayers. In some embodiments, each of zone players 200-204 may also bereferred to as a “smart speaker,” because each zone player containsprocessing capabilities beyond the reproduction of audio, more of whichis described below.

FIG. 2A illustrates a zone player 200 that includes sound producingequipment 208 capable of reproducing full-range sound. The sound maycome from an audio signal that is received and processed by zone player200 over a wired or wireless data network. Sound producing equipment 208includes one or more built-in amplifiers and one or more acoustictransducers (e.g., speakers). A built-in amplifier is described morebelow with respect to FIG. 4. A speaker or acoustic transducer caninclude, for example, any of a tweeter, a mid-range driver, a low-rangedriver, and a subwoofer. In some embodiments, zone player 200 can bestatically or dynamically configured to play stereophonic audio,monaural audio, or both. In some embodiments, zone player 200 may bedynamically configured to reproduce a subset of full-range sound, suchas when zone player 200 is grouped with other zone players to playstereophonic audio, monaural audio, and/or surround audio or when themedia content received by zone player 200 is less than full-range.

FIG. 2B illustrates zone player 202 that includes a built-in amplifierto power and amplify sound to a set of detached speakers 210. A detachedspeaker can include, for example, any type of loudspeaker. Zone player202 may be configured to power one or more separate loudspeakers. Zoneplayer 202 may be configured to communicate an audio signal (e.g., rightand left channel audio or more channels depending on its configuration)to the detached speakers 210 via a wired path.

FIG. 2C illustrates zone player 204 that does not include a built-inamplifier, but is configured to communicate an audio signal, receivedover a data network, to an audio (or “audio/video”) receiver 214 withbuilt-in amplification.

Referring back to FIG. 1, in some embodiments, one, some, or all of thezone players 102 to 124 can retrieve audio directly from a source. Forexample, a particular zone player in a zone or zone group may beassigned to a playback queue (or simply a “queue”). The playback queuegenerally contains information corresponding to one or more audio itemsfor playback by the associated zone or zone group. The playback queuemay be stored in memory on a zone player or some other designateddevice. Each item contained in the playback queue may comprise a uniformresource identifier (URI) or some other identifier that can be used bythe zone player(s) to seek out and/or retrieve the audio items from theidentified audio source(s). Depending on the item, the audio sourcemight be found on the Internet (e.g., the cloud), locally from anotherdevice over the data network 128 (described further below), from thecontroller 130, stored on the zone player itself, or from an audiosource communicating directly to the zone player. In some embodiments,the zone player can reproduce the audio itself (e.g., play the audio),send the audio to another zone player for reproduction or play, or bothwhere the audio is reproduced by the zone player as well as one or moreadditional zone players (possibly in synchrony). In some embodiments,the zone player may play a first audio content (or alternatively, maynot play the content at all), while sending a second, different audiocontent to another zone player(s) for reproduction. To the user, eachitem in a playback queue is represented on an interface of a controllerby an element such as a track name, album name, radio station name,playlist, and/or other some other representation or identification. Auser can populate the playback queue with audio items of interest. Theuser may also modify and clear the playback queue, if so desired, suchthat the queue may be empty.

By way of illustration, SONOS, Inc. of Santa Barbara, Calif. presentlyoffers for sale zone players referred to as a “PLAY:5,” “PLAY:3,”“PLAYBAR,” “CONNECT:AMP,” “CONNECT,” and “SUB.” Any other past, present,and/or future zone players can additionally or alternatively be used toimplement the zone players of example embodiments disclosed herein.Additionally, it is understood that a zone player is not limited to theparticular examples illustrated in FIGS. 2A, 2B, and 2C or to the SONOSproduct offerings. For example, a zone player may include a wired orwireless headphone. In yet another example, a zone player might includea sound bar for television. In yet another example, a zone player mayinclude or interact with a docking station for an Apple iPod™ or similardevices capable of storing and playing video and audio files.

b. Example Controllers

FIG. 3 illustrates an example wireless controller 300 in docking station302. In some instances, wireless controller 300 may be in station modewhile in docking station 302. By way of illustration, controller 300 maycorrespond to controlling device 130 of FIG. 1. Docking station 302, ifprovided or used, may provide power to the controller 300 andadditionally may charge a battery of controller 300. In someembodiments, controller 300 may be provided with a touch screen 304 thatallows a user to interact through touch with the controller 300. Forexample, touch screen 304 may enable the user to retrieve and navigate aplaylist of audio items, modify and/or clear the playback queue of oneor more zone players, control other operations of one or more zoneplayers, and provide overall control of the system configuration 100. Inother embodiments, other input mechanisms such as voice control may beused to interact with the controller 300. In certain embodiments, anynumber of controllers can be used to control the system configuration100. In some embodiments, there may be a limit set on the number ofcontrollers that can control the system configuration 100. Thecontrollers might be wireless similar to that of wireless controller300, wired to data network 128, or capable of both wireless and wiredcommunication. It should be noted that wireless controller 300 may alsobe referred to as a master device, as part of a networked media system.

In some embodiments, if more than one controller is used in system 100of FIG. 1, each controller may be coordinated to display common content.In some instances, one or more controllers may be dynamically updated toindicate changes made to the system 100 from a single controller, e.g.,a master device. Coordination can occur, for instance, by a controllerperiodically requesting a state variable directly or indirectly from oneor more of the zone players; the state variable may provide informationabout system 100, such as current zone group configuration, what isplaying in one or more zones, volume levels, and other items ofinterest. The state variable may be passed around on data network 128between zone players (and controllers, if so desired) as needed or asoften as programmed.

In addition, an application running on any network-enabled portabledevice, such as an iPhone™, iPad™, Android™ powered phone or tablet, orany other smart phone or network-enabled device can be used ascontroller 130. An application running on a laptop or desktop personalcomputer (PC) or Mac™ can also be used as controller 130. Suchcontrollers may connect to system 100 through an interface with datanetwork 128, a zone player, a wireless router, or using some otherconfigured connection path. Example controllers offered by Sonos, Inc.of Santa Barbara, Calif. include a “Controller 200,” “SONOS® CONTROL,”“SONOS® Controller for iPhone™,” “SONOS® Controller for iPad™,” “SONOS®Controller for Android™,” “SONOS® Controller for Mac™ or PC.”

c. Example Data Connection

Zone players 102-124 of FIG. 1 are coupled directly or indirectly to adata network, such as data network 128. Controller 130 may also becoupled directly or indirectly to data network 128 or individual zoneplayers. Data network 128 is represented by an octagon in the figure tostand out from other representative components. While data network 128is shown in a single location, it is understood that such a network canbe distributed in and around system 100. Particularly, data network 128can be a wired network, a wireless network, or a combination of bothwired and wireless networks. In some embodiments, one or more of thezone players 102-124 are wirelessly coupled to data network 128 based ona proprietary mesh network. In some embodiments, one or more of the zoneplayers are coupled to data network 128 using a centralized access pointsuch as a wired or wireless router. In some embodiments, one or more ofthe zone players 102-124 are coupled via a wire to data network 128using Ethernet or similar technology. In addition to the one or morezone players 102-124 connecting to data network 128, data network 128can further allow access to a wide area network, such as the Internet.It should be noted that data network 128 may part of a networked mediasystem.

In some embodiments, connecting any of the zone players 102-124, or someother connecting device, to a broadband router, can create data network128. Other zone players 102-124 can then be added wired or wirelessly tothe data network 128. For example, a zone player (e.g., any one of zoneplayers 102-124) can be added to the system configuration 100 (orperform some other action) by simply pressing a button on the zoneplayer itself, which enables a connection to be made to data network128. The broadband router can be connected to an Internet ServiceProvider (ISP), for example. The broadband router can be used to formanother data network within the system configuration 100, which can beused in other applications (e.g., web surfing or browsing).

Data network 128 can also be used in other applications, if soprogrammed. An example, second network may implement SONOSNET™ protocol,developed by SONOS, Inc. of Santa Barbara. SONOSNET™ represents asecure, AES-encrypted, peer-to-peer wireless mesh network.Alternatively, in certain embodiments, the data network 128 is the samenetwork, such as a traditional wired or wireless network, used for otherapplications in the household.

In some embodiments, data network 128 can be based on the 802.1dspanning tree protocol (STP). Utilizing the STP protocol, any interfacein data network 128 may be classified as a bridge port. However, datanetwork 128 may include proprietary enhancements to support meshingwireless interfaces, e.g., 2.4 GHz and 5 GHz. For example, rather thanclassifying an interface as a bridge port (as noted above for standardSTP protocols), each zone player may be classified as a bridge port.Further, zone players 102-124 may classify ports as different points ina point-to-point (P2P) network. Yet further, zone players 102-124 may beable to utilize these points as entry points into the P2P data network128. In particular, each of zone players 102-124 may maintain the MACaddress of one or more other zone players (e.g., peer playback devices)in data network 128. For communicating amongst zone players, trafficflowing through these points is encapsulated in a P2P header and isforwarded as unicast frames.

d. Example Zone Configurations

A particular zone can contain one or more zone players. For example, thefamily room of FIG. 1 contains two zone players 106 and 108, while thekitchen is shown with one zone player 102. In another example, the hometheater room contains additional zone players to play audio from a 5.1channel or greater audio source (e.g., a movie encoded with 5.1 orgreater audio channels). In some embodiments, one can position a zoneplayer in a room or space and assign the zone player to a new orexisting zone via controller 130. As such, zones may be created,combined with another zone, removed, and given or labeled with aspecific name (e.g., “Kitchen”), all of which may be programmable withcontroller 130. Moreover, in some embodiments, zone configurations maybe dynamically changed even after being configured using controller 130or some other mechanism.

In some embodiments, a “bonded zone” contains two or more zone players,such as the two zone players 106 and 108 in the family room, whereby thetwo zone players 106 and 108 can be configured to play the same audiosource in synchrony. In one example, the two zone players 106 and 108can be paired to play two separate sounds in left and right channels,for example. In other words, the stereo effects of a sound can bereproduced or enhanced through the two zone players 106 and 108, one forthe left sound and the other for the right sound. In another example twoor more zone players can be sonically consolidated to form a single,consolidated zone player. A consolidated zone player (though made up ofmultiple, separate devices) can be configured to process and reproducesound differently than an unconsolidated zone player or zone playersthat are paired, because a consolidated zone player has additionalspeaker drivers from which sound can be passed. The consolidated zoneplayer can further be paired with a single zone player or yet anotherconsolidated zone player. Each playback device of a consolidatedplayback device can be set in a consolidated mode, for example.

In certain embodiments, paired zone players (also referred to as “bondedzone players”) can play audio in synchrony with other zone players inthe same or different zones.

According to some embodiments, zone players may be: grouped,consolidated, paired with other zone players, and/or separated fromother zone players, for example, to obtain a desired configuration. Theactions of grouping, consolidation, and pairing are preferably performedthrough a control interface, such as using controller 130, and not byphysically connecting and re-connecting speaker wire to individualspeakers for creating different configurations. As such, certainembodiments described herein provide a more flexible and dynamicplatform through which sound reproduction can be offered to theend-user.

e. Example Audio Sources

In some embodiments, each zone can play from the same audio source asanother zone or each zone can play from a different audio source. Forexample, someone can be grilling on the patio and listening to jazzmusic via zone player 124, while someone is preparing food in thekitchen and listening to classical music via zone player 102. Further,someone can be in the office listening to the same jazz music via zoneplayer 110 that is playing on the patio via zone player 124. In someembodiments, the jazz music played via zone players 110 and 124 isplayed in synchrony. It should be noted that playing audio in synchronycan refer to playback between zones, allowing an individual to passthrough zones while seamlessly (or substantially seamlessly) listeningto the audio.

For example, considering the scenario above, the individual on the patiomay go inside the house in the middle of a jazz track. For instance, theindividual may leave the patio at a time of 1:54 in the jazz track,i.e., the track has been playing for one minute and fifty-four secondsfrom the beginning of the track. Despite taking time, e.g., a fewminutes, for the individual to walk from the patio to the office, zoneplayer 102 may begin playing the jazz track at 1:54 as the individualenters the office. As such, the individual is able to listen to theentire jazz track regardless of where he/she is located in the house. Infurther examples, zones can be put into a “party mode” such that allassociated zones will play audio in synchrony. It should be noted thatplaying audio in synchrony may also refer to zone players continuouslyand simultaneously playing audio regardless of where individuals are inthe house.

Sources of audio content to be played by zone players 102-124 arenumerous. In some embodiments, audio on a zone player itself may beaccessed and played. In some embodiments, audio on a controller may beaccessed via the data network 128 and played. In some embodiments, musicfrom a personal library stored on a computer or networked-attachedstorage (NAS) may be accessed via the data network 128 and played. Insome embodiments, Internet radio stations, shows, and podcasts may beaccessed via the data network 128 and played. Music or cloud servicesthat let a user stream and/or download music and audio content may beaccessed via the data network 128 and played. Further, music may beobtained from traditional sources, such as a turntable or CD player, viaa line-in connection to a zone player, for example. Audio content mayalso be accessed using a different protocol, such as Airplay™, which isa wireless technology by Apple, Inc., for example. Audio contentreceived from one or more sources can be shared amongst the zone players102 to 124 via data network 128 and/or controller 130. Theabove-disclosed sources of audio content are referred to herein asnetwork-based audio information sources. However, network-based audioinformation sources are not limited thereto.

In some embodiments, the example home theater zone players 116, 118, 120are coupled to an audio information source such as a television 132. Insome examples, the television 132 is used as a source of audio for thehome theater zone players 116, 118, 120, while in other examples audioinformation from the television 132 may be shared with any of the zoneplayers 102-124 in the audio system 100.

III. Example Zone Players

Referring now to FIG. 4, there is shown an example block diagram of azone player 400 in accordance with an embodiment. Zone player 400includes a network interface 402, a processor 408, a memory 410, anaudio processing component 412, and one or more device modules 414 thatinclude a power indicator module 424. Further, zone player 400 includesan audio amplifier 416 and a speaker unit 418 coupled to the audioamplifier 416. FIG. 2A shows an example illustration of such a zoneplayer. Other types of zone players may not include the speaker unit 418(e.g., such as shown in FIG. 2B) or the audio amplifier 416 (e.g., suchas shown in FIG. 2C). Further, it is contemplated that the zone player400 can be integrated into another component. For example, the zoneplayer 400 could be constructed as part of a television, lighting, orsome other device for indoor or outdoor use.

In some embodiments, network interface 402 facilitates a data flowbetween zone player 400 and other devices on a data network 128. In someembodiments, in addition to getting audio from another zone player ordevice on data network 128, zone player 400 may access audio directlyfrom the audio source, such as over a wide area network or on the localnetwork. In some embodiments, the network interface 402 can furtherhandle the address part of each packet so that it gets to the rightdestination or intercepts packets destined for the zone player 400.Accordingly, in certain embodiments, each of the packets includes anInternet Protocol (IP)-based source address as well as an IP-baseddestination address.

In some embodiments, network interface 402 can include one or both of awireless interface 404 and a wired interface 406. The wireless interface404, also referred to as a radio frequency (RF) interface, providesnetwork interface functions for the zone player 400 to wirelesslycommunicate with other devices (e.g., other zone player(s), speaker(s),receiver(s), component(s) associated with the data network 128, and soon) in accordance with a communication protocol (e.g., any wirelessstandard including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac,802.15, 4G mobile communication standard, and so on). Wireless interface404 may include one or more radios. To receive wireless signals and toprovide the wireless signals to the wireless interface 404 and totransmit wireless signals, the zone player 400 includes one or moreantennas 420. The wired interface 406 provides network interfacefunctions for the zone player 400 to communicate over a wire with otherdevices in accordance with a communication protocol (e.g., IEEE 802.3).In some embodiments, a zone player includes multiple wireless 404interfaces. In some embodiments, a zone player includes multiple wired406 interfaces. In some embodiments, a zone player includes both of theinterfaces 404 and 406. In some embodiments, a zone player 400 includesonly the wireless interface 404 or the wired interface 406.

In some embodiments, the processor 408 can be a clock-driven electronicdevice that is configured to process input data according toinstructions stored in memory 410. The memory 410 is data storage thatcan be loaded with one or more software modules 414, which can beexecuted by the processor 408 to achieve certain tasks. In theillustrated embodiment, the memory 410 is a tangible machine-readablemedium storing instructions that can be executed by the processor 408.In some embodiments, a task might be for the zone player 400 to retrieveaudio data from another zone player or a device on a network (e.g.,using a uniform resource locator (URL) or some other identifier). Insome embodiments, a task may be for the zone player 400 to send audiodata to another zone player or device on a network. In some embodiments,a task may be for the zone player 400 to synchronize playback of audiowith one or more additional zone players. In some embodiments, a taskmay be to pair the zone player 400 with one or more zone players tocreate a multi-channel audio environment. Additional or alternativetasks can be achieved via the one or more software module(s) 414 and theprocessor 408.

In some embodiments, one or more power indicator module(s) 424 may beexecuted by the processor 408 to determine a power source for zoneplayer 400. In some instances, power indicator 424 may identify thatzone player 400 is powered by an alternating current (AC) power supply,e.g., a power outlet, possibly while zone player 400 is in a stationmode and docked on a station. Further, in some instances, zone player400 may be a powered by a direct current (DC) power supply, e.g., abattery 426. Yet further, power indicator 424 may identify the level ofpower in battery 426 of zone player 400. It should be noted that variousembodiments herein may facilitate the conservation of battery power, forexample, the power in battery 426. Yet, it should further be understoodthat such embodiments may also facilitate the conservation of energy,for example, if zone player 400 is powered by an AC power supply througha power outlet.

The audio processing component 412 can include one or moredigital-to-analog converters (DAC), an audio preprocessing component, anaudio enhancement component or a digital signal processor, and so on. Insome embodiments, the audio processing component 412 may be part ofprocessor 408. In some embodiments, the audio that is retrieved via thenetwork interface 402 is processed and/or intentionally altered by theaudio processing component 412. Further, the audio processing component412 can produce analog audio signals. The processed analog audio signalsare then provided to the audio amplifier 416 for playback throughspeakers 418. In addition, the audio processing component 412 caninclude circuitry to process analog or digital signals as inputs to playfrom zone player 400, send to another zone player on a network, or bothplay and send to another zone player on the network. An example inputincludes a line-in connection (e.g., an auto-detecting 3.5 mm audioline-in connection).

The audio amplifier 416 is a device(s) that amplifies audio signals to alevel for driving one or more speakers 418. The one or more speakers 418can include an individual transducer (e.g., a “driver”) or a completespeaker system that includes an enclosure including one or more drivers.A particular driver can be a subwoofer (e.g., for low frequencies), amid-range driver (e.g., for middle frequencies), and a tweeter (e.g.,for high frequencies), for example. An enclosure can be sealed orported, for example. Each transducer may be driven by its own individualamplifier.

A commercial example, presently known as the PLAY:5™, is a zone playerwith a built-in amplifier and speakers that is capable of retrievingaudio directly from the source, such as on the Internet or on the localnetwork, for example. In particular, the PLAY:5™ is a five-amp,five-driver speaker system that includes two tweeters, two mid-rangedrivers, and one woofer. When playing audio content via the PLAY:5, theleft audio data of a track is sent out of the left tweeter and leftmid-range driver, the right audio data of a track is sent out of theright tweeter and the right mid-range driver, and mono bass is sent outof the subwoofer. Further, both mid-range drivers and both tweeters havethe same equalization (or substantially the same equalization). That is,they are both sent the same frequencies but from different channels ofaudio. Audio from Internet radio stations, online music and videoservices, downloaded music, analog audio inputs, television, DVD, and soon, can be played from the PLAY:5™.

IV. Example Controller

Referring now to FIG. 5, there is shown an example block diagram forcontroller 500, which can correspond to the controlling device 130 inFIG. 1 and/or wireless controller 300. Controller 500 can be used tofacilitate the control of multi-media applications, automation andothers in a system. In particular, the controller 500 may be configuredto facilitate a selection of a plurality of audio sources available onthe network and enable control of one or more zone players (e.g., thezone players 102-124 in FIG. 1) through a wireless or wired networkinterface 508. According to one embodiment, the wireless communicationsis based on an industry standard (e.g., infrared, radio, wirelessstandards including IEEE 802.11a, 802.11b, 802.11g, 802.11n, 802.11ac,802.15, 4G mobile communication standard, and so on). Further, when aparticular audio is being accessed via the controller 500 or beingplayed via a zone player, a picture (e.g., album art) or any other data,associated with the audio and/or audio source can be transmitted from azone player or other electronic device to controller 500 for display. Itshould be noted that controller 500.

Controller 500 is provided with a screen 502 and an input interface 514that allows a user to interact with the controller 500, for example, tonavigate a playlist of many multimedia items and to control operationsof one or more zone players. The screen 502 on the controller 500 can bean LCD screen, for example. The screen 502 communicates with and iscommanded by a screen driver 504 that is controlled by a microcontroller(e.g., a processor) 506. The memory 510 can be loaded with one or moremodules, e.g., application module 512, power monitor module 514, anddirect route controller module 516. These modules can be executed by themicrocontroller 506 with or without a user input via the user interface514 to achieve certain tasks. In some embodiments, an application module512 can be configured to facilitate grouping a number of selected zoneplayers into a zone group to facilitate synchronized playback amongstthe zone players in the zone group. In some embodiments, an applicationmodule 512 is configured to control the audio sounds (e.g., volume) ofthe zone players in a zone group. In operation, when the microcontroller506 executes one or more of the application modules 512, the screendriver 504 generates control signals to drive the screen 502 to displayan application specific user interface accordingly.

The controller 500 includes a network interface 508 that facilitateswired or wireless communication with a zone player. In some embodiments,the commands such as volume control and audio playback synchronizationare sent via the network interface 508. In some embodiments, a savedzone group configuration is transmitted between a zone player and acontroller via the network interface 508. The controller 500 can controlone or more zone players, such as 102-124 of FIG. 1. There can be morethan one controller for a particular system, and each controller mayshare common information with another controller, or retrieve the commoninformation from a zone player, if such a zone player storesconfiguration data (e.g., such as a state variable). Further, acontroller can be combined with a zone player, integrated into a zoneplayer, and/or one or more zone players can be integrated into acontroller, among other possibilities.

It should be noted that other network-enabled devices such as aniPhone™, iPad™ or any other smart phone or network-enabled device (e.g.,a networked computer such as a PC or Mac™) can also be used as acontroller to interact with or control zone players in a particularenvironment. In some embodiments, a software application or upgrade canbe downloaded onto a network-enabled device to perform the functionsdescribed herein.

In certain embodiments, a user can create a zone group (also referred toas a bonded zone) including at least two zone players from thecontroller 500. The zone players in the zone group can play audio in asynchronized fashion, such that all of the zone players in the zonegroup playback an identical audio source or a list of identical audiosources in a synchronized manner such that no (or substantially no)audible delays or hiccups are to be heard. Similarly, in someembodiments, when a user increases the audio volume of the group fromthe controller 500, the signals or data of increasing the audio volumefor the group are sent to one of the zone players and causes other zoneplayers in the group to be increased together in volume.

A user via the controller 500 can group zone players into a zone groupby activating a “Link Zones” or “Add Zone” soft button, or de-grouping azone group by activating an “Unlink Zones” or “Drop Zone” button. Forexample, one mechanism for ‘joining’ zone players together for audioplayback is to link a number of zone players together to form a group.To link a number of zone players together, a user can manually link eachzone player or room one after the other. For example, assume that thereis a multi-zone system that includes the following zones: Bathroom,Bedroom, Den, Dining Room, Family Room, and Foyer. In certainembodiments, a user can link any number of the six zone players, forexample, by starting with a single zone and then manually linking eachzone to that zone.

In certain embodiments, a set of zones can be dynamically linkedtogether using a command to create a zone scene or theme (subsequent tofirst creating the zone scene). For instance, a “Morning” zone scenecommand can link the Bedroom, Office, and Kitchen zones together in oneaction. Without this single command, the user would manually andindividually link each zone. The single command may include a mouseclick, a double mouse click, a button press, a gesture, or some otherprogrammed or learned action. Other kinds of zone scenes can beprogrammed or learned by the system over time.

In certain embodiments, a zone scene can be triggered based on time(e.g., an alarm clock function). For instance, a zone scene can be setto apply at 8:00 am. The system can link appropriate zonesautomatically, set specific music to play, and then stop the music aftera defined duration and revert the zones to their prior configuration.Although any particular zone can be triggered to an “On” or “Off” statebased on time, for example, a zone scene enables any zone(s) linked tothe scene to play a predefined audio (e.g., a favorable song, apredefined playlist) at a specific time and/or for a specific duration.If, for any reason, the scheduled music failed to be played (e.g., anempty playlist, no connection to a share, failed Universal Plug and Play(UPnP), no Internet connection for an Internet Radio station, and soon), a backup buzzer can be programmed to sound. The buzzer can includea sound file that is stored in a zone player, for example.

V. Playback Queue

As discussed above, in some embodiments, a zone player may be assignedto a playback queue identifying zero or more media items for playback bythe zone player. The media items identified in a playback queue may berepresented to the user via an interface on a controller. For instance,the representation may show the user (or users if more than onecontroller is connected to the system) how the zone player is traversingthe playback queue, such as by highlighting the “now playing” item,graying out the previously played item(s), highlighting the to-be-playeditem(s), and so on.

In some embodiments, a single zone player is assigned to a playbackqueue. For example, zone player 114 in the bathroom of FIG. 1 may belinked or assigned to a “Bathroom” playback queue. In an embodiment, the“Bathroom” playback queue might have been established by the system as aresult of the user naming the zone player 114 to be association with thebathroom. As such, contents populated and identified in the “Bathroom”playback queue can be played via the zone player 114 (the bathroomzone).

In some embodiments, a zone or zone group is assigned to a playbackqueue. For example, zone players 106 and 108 in the family room of FIG.1 may be linked or assigned to a “Family room” playback queue. Inanother example, if family room and dining room zones were grouped, thenthe new group would be linked or assigned to a “family room +diningroom” playback queue. In some embodiments, the family room+dining roomplayback queue would be established based upon the creation of thegroup. In some embodiments, upon establishment of the new group, thefamily room+dining room playback queue can automatically include thecontents of one (or both) of the playback queues associated with eitherthe family room or dining room or both. In one instance, if the userstarted with the family room and added the dining room, then thecontents of the family room playback queue would become the contents ofthe family room+dining room playback queue. In another instance, if theuser started with the family room and added the dining room, then thefamily room playback queue would be renamed to the family room+diningroom playback queue. If the new group was “ungrouped,” then the familyroom+dining room playback queue may be removed from the system and/orrenamed to one of the zones (e.g., renamed to “family room” or “diningroom”). After ungrouping, each of the family room and the dining roomwill be assigned to a separate playback queue. One or more of the zoneplayers in the zone or zone group may store in memory the associatedplayback queue.

As such, when zones or zone groups are “grouped” or “ungrouped”dynamically by the user via a controller, the system will, in someembodiments, establish or remove/rename playback queues respectively, aseach zone or zone group is to be assigned to a playback queue. In otherwords, the playback queue operates as a container that can be populatedwith media items for playback by the assigned zone. In some embodiments,the media items identified in a playback queue can be manipulated (e.g.,re-arranged, added to, deleted from, and so on).

By way of illustration, FIG. 6 shows an example network media system 600for media content playback. As shown, the example media system network600 includes example zone players 612 and 614, example audio sources 662and 664, and example media items 620. The example media items 620 mayinclude playlist 622, music track 624, Internet radio station 626,playlists 628 and 630, and album 632. In one embodiment, the zoneplayers 612 and 614 may be any of the zone players shown in FIGS. 1,2A-C, and 4. For instance, zone players 612 and 614 may be the zoneplayers 106 and 108, respectively, in the Family Room of FIG. 1.

In one example, the example audio sources 662 and 664, and example mediaitems 620 may be partially stored on a cloud network, discussed morebelow in connection to FIG. 8. In some cases, the portions of the audiosources 662, 664, and example media items 620 may be stored locally onone or both of the zone players 612 and 614. In one embodiment, playlist622, favorite Internet radio station 626, and playlist 630 may be storedlocally, and music track 624, playlist 628, and album 632 may be storedon the cloud network.

Each of the example media items 620 may be a list of media itemsplayable by a zone player(s). In one embodiment, the example media itemsmay be a collection of links or pointers (i.e., URI) to the underlyingdata for media items that are stored elsewhere, such as the audiosources 662 and 664. In another embodiment, the media items may includepointers to media content stored on the local zone player, another zoneplayer over a local network, or a controller device connected to thelocal network.

As shown, the example network 600 may also include an example queue 602associated with the zone player 612, and an example queue 604 associatedwith the zone player 614. Queue 606 may be associated with a group, whenin existence, comprising zone players 612 and 614. Queue 606 mightcomprise a new queue or may exist as a renamed version of queue 602 or604. In some embodiments, in a group, the zone players 612 and 614 wouldbe assigned to queue 606 and queue 602 and 604 would not be available atthat time. In some embodiments, when the group is no longer inexistence, queue 606 is no longer available. Each zone player and eachcombination of zone players in a network of zone players, such as thoseshown in FIG. 1 or that of example zone players 612, 614, and examplecombination 616, may be uniquely assigned to a corresponding playbackqueue.

A playback queue, such as playback queues 602-606, may includeidentification of media content to be played by the corresponding zoneplayer or combination of zone players. As such, media items added to theplayback queue are to be played by the corresponding zone player orcombination of zone players. The zone player may be configured to playitems in the queue according to a specific order (such as an order inwhich the items were added), in a random order, or in some other order.

The playback queue may include a combination of playlists and othermedia items added to the queue. In one embodiment, the items in playbackqueue 602 to be played by the zone player 612 may include items from theaudio sources 662, 664, or any of the media items 622-632. The playbackqueue 602 may also include items stored locally on the zone player 612,or items accessible from the zone player 614. For instance, the playbackqueue 602 may include Internet radio 626 and album 632 items from audiosource 662, and items stored on the zone player 612.

When a media item is added to the queue via an interface of acontroller, a link to the item may be added to the queue. In a case ofadding a playlist to the queue, links to the media items in the playlistmay be provided to the queue. For example, the playback queue 602 mayinclude pointers from the Internet radio 626 and album 632, pointers toitems on the audio source 662, and pointers to items on the zone player612. In another case, a link to the playlist, for example, rather than alink to the media items in the playlist may be provided to the queue,and the zone player or combination of zone players may play the mediaitems in the playlist by accessing the media items via the playlist. Forexample, the album 632 may include pointers to items stored on audiosource 662. Rather than adding links to the items on audio source 662, alink to the album 632 may be added to the playback queue 602, such thatthe zone player 612 may play the items on the audio source 662 byaccessing the items via pointers in the album 632.

In some cases, contents may be stored as a playlist. Further, at a givenpoint in time within a playback queue, such contents may be stored as aplaylist, and subsequently added to the same queue later or added toanother queue. For example, contents of the playback queue 602, at aparticular point in time, may be saved as a playlist, stored locally onthe zone player 612 and/or on the cloud network. The saved playlist maythen be added to playback queue 604 to be played by zone player 614.

VI. Example Ad-Hoc Network

Particular examples are now provided in connection with FIG. 7 todescribe, for purposes of illustration, certain embodiments to provideand facilitate connection to a playback network. FIG. 7 shows that thereare three zone players 702, 704 and 706 and a controller 708 that form anetwork branch that is also referred to as an Ad-Hoc network 710. Thenetwork 710 may be wireless, wired, or a combination of wired andwireless technologies. In general, an Ad-Hoc (or “spontaneous”) networkis a local area network or other small network in which there isgenerally no one access point for all traffic. With an establishedAd-Hoc network 710, the devices 702, 704, 706 and 708 can allcommunicate with each other through direct point-to-point communicationroutes (e.g., in a “peer-to-peer” style of communication), for example.Furthermore, devices may join and/or leave from the network 710, and thenetwork 710 will automatically reconfigure itself without needing theuser to reconfigure the network 710. While an Ad-Hoc network isreferenced in FIG. 7, it is understood that a playback network may bebased on a type of network that is completely or partially differentfrom an Ad-Hoc network. It should be noted that networked media systemsdescribed herein may include Ad-Hoc networks such as Ad-Hoc network 710.

Using the Ad-Hoc network 710, the devices 702, 704, 706, and 708 canshare or exchange one or more audio sources and can be dynamicallygrouped (or ungrouped) to play the same or different audio sources. Forexample, the devices 702 and 704 are grouped to playback one piece ofmusic, and at the same time, the device 706 plays back another piece ofmusic. In other words, the devices 702, 704, 706 and 708, as shown inFIG. 7, form a HOUSEHOLD that distributes audio and/or reproduces sound.As used herein, the term HOUSEHOLD (provided in uppercase letters todisambiguate from the user's domicile) is used to represent a collectionof networked devices that are cooperating to provide an application orservice. An instance of a HOUSEHOLD is identified with a household 710(or household identifier), though a HOUSEHOLD may be identified with adifferent area or place.

In certain embodiments, a household identifier (HHID) is a short stringor an identifier that is computer-generated to help ensure that it isunique. Accordingly, the network 710 can be characterized by a uniqueHHID and a unique set of configuration variables or parameters, such aschannels (e.g., respective frequency bands), service set identifier(SSID) (a sequence of alphanumeric characters as a name of a wirelessnetwork), and WEP keys (wired equivalent privacy) or other securitykeys. In certain embodiments, SSID is set to be the same as HHID.

In certain embodiments, each HOUSEHOLD can include two types of networknodes: a control point (CP) and a zone player (ZP). The control pointcontrols an overall network setup process and sequencing, including anautomatic generation of required network parameters (e.g., securitykeys). In an embodiment, the CP also provides the user with a HOUSEHOLDconfiguration user interface. The CP function can be provided by acomputer running a CP application module, or by a handheld controller(e.g., the controller 308) also running a CP application module, forexample. The zone player is any other device on the network that isplaced to participate in the automatic configuration process. The ZP, asa notation used herein, includes the controller 308 or a computingdevice, for example. In some embodiments, the functionality, or certainparts of the functionality, in both the CP and the ZP are combined at asingle node (e.g., a ZP contains a CP or vice-versa).

In certain embodiments, configuration of a HOUSEHOLD involves multipleCPs and ZPs that rendezvous and establish a known configuration suchthat they can use a standard networking protocol (e.g., IP over Wired orWireless Ethernet) for communication. In an embodiment, two types ofnetworks/protocols are employed: Ethernet 802.3 and Wireless 802.11g.Interconnections between a CP and a ZP can use either of thenetworks/protocols. A device in the system as a member of a HOUSEHOLDcan connect to both networks simultaneously.

In an environment that has both networks in use, it is assumed that atleast one device in a system is connected as a bridging device, thusproviding bridging services between wired/wireless networks for others.The zone player 706 in FIG. 7 is shown to be connected to both networks,for example. The connectivity to the network 712 is based on Ethernetand/or Wireless, while the connectivity to other devices 702, 704 and708 is based on Wireless and Ethernet if so desired.

It is understood, however, that in some embodiments, each zone player706, 704, 702 may access the Internet when retrieving media from thecloud (e.g., the Internet) via the bridging device. For example, zoneplayer 702 may contain a uniform resource locator (URL) that specifiesan address to a particular audio track in the cloud. Using the URL, thezone player 702 may retrieve the audio track from the cloud, andultimately play the audio out of one or more zone players.

VII. Another Example System Configuration

FIG. 8 shows a system 800 including a plurality of interconnectednetworks including a cloud-based network and at least one local playbacknetwork. A local playback network includes a plurality of playbackdevices or players, though it is understood that the playback networkmay contain only one playback device. In certain embodiments, eachplayer has an ability to retrieve its content for playback. Control andcontent retrieval can be distributed or centralized, for example. Inputcan include streaming content provider input, third party applicationinput, mobile device input, user input, and/or other playback networkinput into the cloud for local distribution and playback.

As illustrated by the example system 800 of FIG. 8, a plurality ofcontent providers 820-850 can be connected to one or more local playbacknetworks 860-870 via a cloud and/or other network 810. Using the cloud810, a multimedia audio system server 820 (e.g., Sonos™) a mobile device830, a third party application 840, a content provider 850 and so on canprovide multimedia content (requested or otherwise) to local playbacknetworks 860, 870. Within each local playback network 860, 870, acontroller 862, 872 and a playback device 864, 874 can be used toplayback audio content.

VIII. Utilizing Direct and Non-Direct Routes Based on Low PowerOperation

As described above, embodiments described herein involve communicationroutes between playback devices of a networked media system. Further, asnoted above, the network media system may be configured to utilizedirect communication routes (such as communication routes configuredusing a spanning tree protocol (STP)) and/or non-direct communicationroutes (such as a point-to-point communication route). Yet further, suchdirect routes and non-direct routes may be utilized in accordance withvarious types of device modes, such as a low power mode.

FIG. 9 shows an example networked media system. The networked mediasystem 900 includes direct routes (e.g., point-to-point routes) andnon-direct routes (e.g., spanning tree protocol (STP) routes). Asdesignated in legend 902, direct routes are illustrated by dashed linesand STP routes are illustrated by solid lines. Further, networked mediasystem 900 includes wireless router 904 that is directly routed tocomputer 914 and tablet 916. Yet further, networked media system 900 mayutilize a mesh networking topology to place playback devices 906, 908,910, and 912 in communication with each other using both STP routes anddirect routes. For purposes of illustration, STP routes in networkedmedia system 1000 are identified by STP links 920, 924, 930, and 932.For example, playback device 906 is routed to wireless router 904 andplayback device 908 via STP links 920 and 924, respectively. As anotherexample, playback device 910 is routed to playback devices 908 and 912via STP links 930 and 932, respectively.

The example networked media system 900 also includes direct routes 926and 928, among other (non-enumerated) direct routes. For example,playback device 912 is directly routed to playback device 906 via directlink 928. Further, playback device 910 is directly routed to playbackdevice 906 via direct link 926. Although not shown, other direct linksmay exist as well. For example, playback device 912 could be directlyrouted to playback device 908, among other possibilities.

Playback devices 906, 908, 910, and 912 can be controlled using one ormore controllers such as computer 914, tablet 916, and wirelesscontroller 918. To facilitate discussion of method 1000 described below,playback device 912 may be referred to herein as a first playbackdevice. Further, any one of playback devices 906, 908, and 910 may bereferred to as at least one additional playback device. Yet further, acontroller device, such as any one of computer 914, tablet 916, andwireless controller 918, may also include a playback device that may bereferred to herein as a third playback device.

FIG. 10 shows an example flow diagram for intelligently utilizingcommunication routes based low power operation, in accordance with atleast some embodiments described herein. Method 1000 shown in FIG. 10presents an embodiment of a method that could be used in environments100, 600, 700, 800, 900 and 1200, and possibly in association withsystems 200, 202, 204, 300, 400, and 500, for example, for communicationwith one or more playback devices.

As a general matter, each of blocks 1002-1012 may be carried out by oneor more playback devices. Playback devices may include any one or moreof zone players 102-124 of FIG. 1. Further, playback devices may includeany one or more of zone players 200, 202, and 204 of FIGS. 2A, 2B, and2C, respectfully. Yet further, playback devices may include any one ormore of zone players 400 of FIG. 4 and zone players 612 and 614 of FIG.6. In addition, playback devices may also include any one or more ofzone players 702-706 of FIG. 7 and/or playback devices 864 and 874 ofFIG. 8. In some instances, playback devices may include wirelesscontroller 300, controller 500, and wireless controller 918 of FIGS. 3,5, and 9, respectively. In addition, playback devices may includeplayback devices 906-912 of FIG. 9, and possibly computer 914 and tablet916. Other possibilities may also exist. It should be understood thatplayback devices may be described herein as a “first playback device”, a“second playback device”, “at least one additional playback device”,and/or “a third playback device” to distinguish one playback device fromanother.

Method 1000 may include one or more operations, functions, or actions asillustrated by one or more of blocks 1002-1012. Although the blocks areillustrated in sequential order, these blocks may also be performed inparallel, and/or in a different order than those described herein. Also,the various blocks may be combined into fewer blocks, divided intoadditional blocks, and/or removed based upon a desired implementation.It should also be noted that a first playback device may perform one ormore of blocks 1002-1012 and the first playback device may instructanother playback device to perform the other blocks of 1002-1012, amongother possibilities.

In addition, for the method 1000 and other processes and methodsdisclosed herein, the flowchart shows functionality and operation of onepossible implementation of present embodiments. In this regard, eachblock may represent a module, a segment, or a portion of program code,which includes one or more instructions executable by a processor forimplementing specific logical functions or steps in the process. Theprogram code may be stored on any type of computer readable medium, forexample, such as a storage device including a disk or hard drive. Thecomputer readable medium may include non-transitory computer readablemedium, for example, such as computer-readable media that stores datafor short periods of time like register memory, processor cache andRandom Access Memory (RAM). The computer readable medium may alsoinclude non-transitory media, such as secondary or persistent long termstorage, like read only memory (ROM), optical or magnetic disks,compact-disc read only memory (CD-ROM), for example. The computerreadable media may also be any other volatile or non-volatile storagesystems. The computer readable medium may be considered a computerreadable storage medium, for example, or a tangible storage device. Inaddition, for the method 1000 and other processes and methods disclosedherein, each block in FIG. 9 may represent circuitry that is wired toperform the specific logical functions in the process.

At block 1002, the method 1000 may involve determining, by a firstplayback device that is part of a networked media system, that the firstplayback device should enter a low power mode. As described above, afirst playback device may be powered by a battery. For example,referring back to FIG. 4, zone player 400 may be powered by battery 426.Further, power indicator module 424 may be executed by processor 408 todetermine the level of power remaining in battery 426 at various pointsin time. In some instances, power indicator module 424 may provideinformation corresponding to an amount of time left before the powerremaining in battery 426 is estimated to run out, possibly based on thedevice mode of zone player 400 and/or the ports used by zone player 400to communicate with other zone players.

In some embodiments, the first playback device may be configured toenter various device modes. As a general matter, a device mode may beindicative of a state of the playback device, in accordance with itsfunctionality and/or configuration at a given point in time. Forexample, the first playback device may be configured to enter a lowpower mode. Such low power modes may include standby mode, fallbackmode, sleep mode, snooze mode, hibernation mode, power down mode, and/ortravel mode (e.g., airplane mode), among other possibilities. It shouldbe understood that although the method 1000 is described with respect toa low power mode, it could be utilized for other device modes as well.

As noted above, zone player 400 may include power indicator module 424that may be executed by processor 408. In some instances, based onexecuting power indicator module 424, processor 408 may change thedevice mode of zone player 400 from one device mode (e.g., station mode,normal-operating mode, and speed mode) to different device mode (e.g.,low power mode).

In some embodiments, the first playback device may be configured todetermine that it should enter a low power mode. For example, powerindicator module 424 of zone player 400 may indicate that the level ofremaining power in battery 426 is less than or equal to a thresholdlevel of power. As such, zone player 400 may determine that it shouldenter a low power mode to conserve the power remaining in battery 426.

In some instances, the first playback device may determine that itshould enter the low power mode after not playing audio content for aspecified period of time, possibly a threshold period of time. Forexample, zone player 400 may enter the low power mode after five minutesof not playing audio content or some other period of time that may bespecified by a given user. As another example, the first playback devicemay determine that it should enter the low power mode if it is notproviding audio content to another playback device. It should beunderstood that a combination of the thresholds described above (orother thresholds not expressly provided) may also be implemented. Forexample, zone player 400 may determine that it should enter the lowpower mode when (i) the level of remaining power in battery 426 is lessthan or equal to a threshold level of power, (ii) zone player 400 is notplaying back audio content, and (iii) zone player 400 is not providingaudio content to another zone player. Other possibilities and/orcombinations are possible as well.

Based on the determination at block 1002, the method 1000 at block 1004may involve identifying, by the first playback device, at least oneadditional playback device that is part of the networked media system,where the first playback device is configured to communicate with the atleast one additional playback device via (i) a first route, and (ii) asecond route. For example, referring back to FIG. 9, playback device 912(e.g., the first playback device) may identify playback device 906 ofnetworked media system 900. As such, playback device 912 may be able tocommunicate with playback device 906 via a first route. The first routemay be a direct point-to-point route, such as direct route 928. Thesecond route may be a non-direct communication route. For example,playback device 912 may communicate with playback device 906 using asecond, non-direct route via playback devices 910 and 908. This second,non-direct route may utilize STP links 932, 930, and 924.

At block 1006, the method 1000 may involve informing, by the firstplayback device, at least one additional playback device not to utilizethe first route with the first playback device. For example, consideringone or more scenarios of FIG. 9 above, playback device 912 may determinethat it should enter the low power mode. As such, playback device 912may inform playback device 906 not to utilize direct route 928 tocommunicate with playback device 912. Thus, playback device 906 may belimited to utilizing STP links 924, 930 and 932 to communicate withplayback device 912, while utilizing playback devices 908 and 910 asintermediary devices. In some embodiments, playback device 912 mayreceive a confirmation or an answer from playback device 906 thatplayback device 906 will not utilize direct route 928 to communicatewith playback device 912.

In a further example, as part of informing the at least one additionalplayback device not to utilize the first route with the first playbackdevice, the first playback device may inform the at least one additionalplayback device to avoid routing communication through the firstplayback device, if possible. For example, if there are devicesconnected to the first playback device that are reachable by routesother than via the first playback device, then those routes should beused.

At block 1008, the method 1000 may involve entering, by the firstplayback device, the low power mode. For example, considering one ormore scenarios of FIG. 9 above, playback device 912 may enter the lowpower mode.

Referring back to FIG. 4, for an example of entering the low power mode,processor 408 may execute one or more modules 414. In particular,processor 408 may execute power indicator module 424 such that zoneplayer 400 enters the low power mode. Entering the low power mode mayallow zone player 400 to conserve the remaining power left in battery426. In some instances, the low power mode may also disable and/orsuspend power for various components such as audio processing component412, audio amplifier(s) 416, and/or speaker(s) 418.

FIG. 11A shows an illustration of an example bridge table entry and FIG.11B shows an illustration of an example bridge table entry based on lowpower operation. For example, bridge table entry 1102 may beperiodically updated by playback device 912, possibly based on a clockor a timer. As illustrated in FIG. 11A, prior to playback device 912entering the low power mode, bridge table entry 1102 includes port IDsdesignated as Port_928 and Port_932 for communicating with each of therespective playback devices 906 and 910 in FIG. 9.

Further, bridge table entry 1102 includes MAC addresses designated asPlayback_906 and Playback_910 for each of the respective playbackdevices 906 and 910 in FIG. 9. It should be understood that as a generalmatter, a MAC address may include a 48-bit address space unique to eachplayback device, but nonetheless, the representation of MAC addresses inFIGS. 11A-E are provided for simplicity and illustrative purposes. Yetfurther, bridge table entry 1102 includes at least one route typeincluding, but not limited to, STP protocol and/or direct routing foreach port. Yet further, bridge table entry 1102 may designate port typesas point-to-point (P2P) wireless ports or wired ports, among otherpossibilities.

As illustrated in FIG. 11B, after entering the low power mode, bridgetable entry 1104 includes the port ID of Port_932 but other Port IDs,such as Port_928, may no longer be present. Further, bridge table entry1104 includes the MAC address of Playback_910, but other MAC addresses,such as Playback_906, may no longer be present. By omitting such data inbridge table entry 1104, playback device 912 does not update theinformation for various devices (e.g., playback device 906) while in lowpower mode. As opposed to probing for additional playback devices, aspossibly done while operating in station mode or normal operating mode,playback device 912 may instead disable its probing to conserve powerand energy in low power mode. Yet further, playback device 912 may notneed to maintain network properties associated with wirelessconnectivity, e.g., authentication levels, data encryption, and signalquality, among other activities that may consume power and energy. Insome instances, playback device 912 may only maintain the information ofplayback device 910 in bridge table 1104 to synchronize with playbackdevice 910 when exiting the low power mode.

FIG. 11C shows an illustration of another example bridge table entry andFIG. 11D shows an illustration of another example bridge table entrybased on low power operation. For example, bridge table entry 1106 maybe periodically updated by playback device 906, possibly based on aclock or a timer. As illustrated in FIG. 11C, prior to playback device906 entering the low power mode, bridge table entry 1106 includes portIDs designated Port_924, Port_926, and Port_928 for communicating witheach of the respective playback devices 908, 910, and 912 in FIG. 9. Yetfurther, bridge table entry 1106 includes the port ID of Port_920 forcommunicating with the wireless router 904. In this example embodiment,playback device 906 may be connected to wireless router 904 via wiredconnection 920 (possibly a wired Ethernet connection) and a MAC addressmay not be recorded for wired connections. In other example embodiments,a MAC address may be recorded for wired connections.

Further, bridge table entry 1106 includes MAC addresses designated asPlayback_908, Playback_910, and Playback_912 for each of the respectiveplayback devices 908, 910, and 912 in FIG. 9. Yet further, bridge tableentry 1106 includes at least one route type including, but not limitedto, an STP protocol and/or direct routing for each port. Yet further,bridge table entry 1106 may designate port types as point-to-point (P2P)wireless communication ports and/or wired ports, among otherpossibilities.

As illustrated in FIG. 11D, after playback device 906 enters the lowpower mode, bridge table entry 1108 includes the port IDs of Port_924and Port_920, but other Port IDs, such as Port_926 and Port_928, may nolonger be present. Further, bridge table entry 1108 includes the MACaddress of Playback_908, but other MAC addresses such as Playback_910and Playback_912, may no longer be present. By omitting such data inbridge table entry 1108, playback device 906 does not update theinformation for various devices (e.g., playback devices 910 and 912)while in low power mode. As opposed to probing for additional playbackdevices, as possibly done while operating in station mode or normaloperating mode, playback device 906 may instead disable its probing toconserve power and energy in low power mode. Yet further, playbackdevice 906 may not need to maintain network properties associated withwireless connectivity, e.g., authentication levels, data encryption, andsignal quality, among other activities that may consume the power andenergy. In some instances, playback device 906 may only maintain theinformation of playback device 908 and/or wireless router 904 in bridgetable 1104 to synchronize with playback device 908 and/or wirelessrouter 904 when exiting the low power mode.

FIG. 12A shows another example networked media system. The networkedmedia system 1200 includes direct routes (e.g., point-to-point routes)and non-direct routes (e.g., spanning tree protocol (STP) routes). Asdesignated in legend 1202, a direct route is illustrated by a dashedline and STP routes are illustrated in solid lines. Further, networkedmedia system 1200 includes wireless router 1204 that is directly routedto playback devices 1206 and 1208. In this example embodiment, thewireless router 1204 is connected wirelessly to playback devices 1206and 1208. In other embodiments, the wireless router 1204 may beconnected wirelessly or via a wired technology (e.g., Ethernet) toplayback devices 1206 and 1208. Yet further, networked media system 1200may utilize a mesh networking topology to place playback devices 1206and 1208 in communication with each other using direct route 1240. Forpurposes of illustration, playback device 1206 is routed to wirelessrouter 1204 via STP link 1220. Further, playback device 1208 is routedto wireless router 1204 via STP link 1230. To facilitate discussion ofmethod 1000 described herein, playback device 1206 may be referred toherein as a first playback device. Further, playback device 1208 may bereferred to at least one additional playback device. Yet further,wireless router 1204 may also include a playback device that may bereferred to herein as a third playback device.

FIG. 12B shows an illustration of yet another example bridge table entryand FIG. 12C shows an illustration of yet another example bridge tableentry based on low power operation. For example, bridge table entry 1242may be periodically updated by playback device 1206, possibly based on aclock or a timer. As illustrated in FIG. 11A, prior to playback device1206 entering the low power mode, bridge table entry 1242 includes portIDs designated as Port_1220 and Port_1240 for communicating withwireless router 1204 and playback device 1208 in FIG. 12A, respectively.

Further, bridge table entry 1242 includes MAC addresses designated aswireless 1204 and Playback_1208 for wireless router 1204 and playbackdevice 1208 in FIG. 12A, respectively. In this example, as opposed toone or more previous examples described, the MAC address assigned to thewireless router 1204 (Wireless_1204) may be recorded in the bridge tableentry 1242 because the connection between the playback device 1206 andthe wireless router 1204 is a wireless connection. As noted for FIGS.11A-D, a MAC address may include a 48-bit address space unique to eachplayback device, but nonetheless, the representation of MAC addresses inFIGS. 12B and 12C are provided for simplicity and illustrative purposes.Yet further, bridge table entry 1242 includes at least one route typeincluding, but not limited to, “access point” and/or direct routing foreach port. Yet further, bridge table entry 1242 may designate port typesas access point (AP) and/or point-to-point (P2P) wireless communicationports, among other possibilities.

As illustrated in FIG. 12B, after playback device 1206 enters the lowpower mode, bridge table entry 1244 includes the port ID of Port_1220but Port_1240 may no longer be present. Further, bridge table entry 1244includes the MAC address of Wireless_1204, but other MAC addresses, suchas Playback_1208, may no longer be present. By omitting such data inbridge table entry 1244, playback device 1206 does not update theinformation for various devices (e.g., playback device 1208) while inlow power mode. As opposed to probing for additional playback devices,as possibly done while operating in station mode or normal operatingmode, playback device 1206 may instead disable its probing to conservepower and energy in low power mode. Yet further, playback device 1206may not need to maintain network properties associated with wirelessconnectivity, e.g., authentication levels, data encryption, and signalquality, among other activities that may consume the power and energy.In some instances, playback device 1206 may only maintain theinformation of wireless router 1204 to synchronize with wireless router1204 when exiting the low power mode.

At block 1010, the method 1000 may involve periodically receiving, bythe first playback device, a message from a master device, where themaster device is part of the networked media system. For example,considering one or more scenarios of FIG. 9 above, playback device 912may enter the low power mode and may periodically receive a message froma master device, such as playback device 906. Generally, the masterdevice will be a playback device that is a parent node to the firstplayback device. As shown in FIG. 9, playback devices 906, 908, and 910may all be parent nodes to playback device 912. As such, any of thesedevices could serve as master devices. In one embodiment, a masterdevice could be the playback device farthest up the spanning tree, e.g.,playback device 906 that is routed to wireless router 904. In anotherembodiment, a master device could be the playback device immediately upthe spanning tree, e.g., playback devices 906, 908 and/or 910. Otherembodiments are possible as well. In some embodiments, a master devicecan also be configured to send commands that cause one or more playbackdevices in low power mode to exit the low power mode, possibly to enteranother device mode.

In some instances, the master node (in this example playback device 906)may communicate with each of playback devices 908, 910, and 912 todetermine and/or monitor the power level of each respective playbackdevice. For example, playback device 912 may determine that its powerlevel has dropped under a threshold level of power. As such, playbackdevice 912 may enter low power mode and thus no longer utilize directroute 928. However, playback device 912 may be recharged, possibly by auser, to increase its power level above the threshold level of power. Ifthe master device is monitoring the level of power of playback device912, it could instruct playback device 912 to exit the low power mode,possibly to enter normal operating modes. As another example, playbackdevice 912 could be configured to automatically exit the lower powermode upon reaching a threshold level of power.

In some embodiments, as noted above, playback devices may maintain theidentification of a master device or node to receive network informationfrom the master device when exiting the low power mode. For example,playback device 912 may go into low power mode such and playback device912 may include bridge table entry 1104, as shown in FIG. 11B. Further,playback device 912 may receive a wake-on-wireless (WOW) message fromplayback device 906, possibly a master device. In response, playbackdevice 912 may update its bridge table entry 1104 using the dataprovided in the WOW message. Thus, playback device 912 may again obtainthe data shown in bridge table entry 1102.

At block 1012, the method 1000 may involve exiting, by the firstplayback device, the low power mode. For example, considering one ormore scenarios of FIG. 9 above, playback device 912 may exit the lowpower mode. In some instances, playback device 912 may exit the lowpower mode and enter one or more normal operating modes.

In some embodiments, based on exiting the lower power mode, the firstplayback device may inform at least one additional playback device toreutilize the first route (i.e., direct route) with the first playbackdevice. For example, considering one or more scenarios of FIG. 9 above,playback device 912 may exit the low power mode and inform playbackdevice 906 to reutilize direct route 928.

Further, considering one or more scenarios of FIG. 9 above, playbackdevice 912 may enter a low power mode and subsequently recharge itsbatteries above a threshold level of power. As such, playback devices912 may exit the low power mode. As noted above, a master device, suchas playback device 906, may monitor the power levels of one or moreplayback devices and send messages to playback device 912 to exit thelow power mode. In some instances, the master device may send one ormore messages to playback device 912 to enable direct route 928. Assuch, playback devices 912 may reutilize direct route 928. Further,playback device 912 may update its bridge table entry 1104 using thedata provided by the master device. Thus, playback device 912 may againobtain the data shown in bridge table entry 1102.

IX. Conclusion

The descriptions above disclose various example systems, methods,apparatus, and articles of manufacture including, among othercomponents, firmware and/or software executed on hardware. However, suchexamples are merely illustrative and should not be considered aslimiting. For example, it is contemplated that any or all of thesefirmware, hardware, and/or software components can be embodiedexclusively in hardware, exclusively in software, exclusively infirmware, or in any combination of hardware, software, and/or firmware.Accordingly, while the following describes example systems, methods,apparatus, and/or articles of manufacture, the examples provided are notthe only way(s) to implement such systems, methods, apparatus, and/orarticles of manufacture.

As described above, embodiments described herein involve communicationroutes between playback devices of a networked media system. Further, asnoted above, an example network media system may be configured withdirect communication routes and/or non-direct communication routes, inaccordance with the spanning tree protocol (STP). Yet further, suchdirect routes and non-direct routes may be utilized in accordance withvarious types of device modes, such as a low power mode.

In one aspect, a method is provided. The method involves determining, bya first playback device, that the first playback device should enter alow power mode, where the first playback device is part of a networkedmedia system. Based on this determination, the method further involvesidentifying, by the first playback device, at least one additionalplayback device that is part of the networked media system, where thefirst playback device is configured to communicate with the at least oneadditional playback device via (i) a first route, and (ii) a secondroute. Further, the method involves informing, by the first playbackdevice, the at least one additional playback device not to utilize thefirst route with the first playback device. Yet further, the methodinvolves entering, by the first playback device, the low power mode.While the first playback device is in the low power mode, the methodfurther involves periodically receiving, by the first playback device, amessage from a master device, where the master device is part of thenetworked media system. Based on the message, the method involvesexiting, by the first playback device, the low power mode.

In another aspect, a playback device is provided. The playback deviceincludes a processor, a network interface, a non-transitorycomputer-readable storage medium, and program logic stored on thenon-transitory computer-readable medium. The program logic is executableby the processor to determine that the playback device should enter alow power mode, where the playback device is part of a networked mediasystem. Based on the determination, the program logic is furtherexecutable by the processor to identify at least one additional playbackdevice that is part of the networked media system, where the playbackdevice is configured to communicate with the at least one additionalplayback device via (i) a first route, and (ii) a second route. Theprogram logic is further executable by the processor to inform the atleast one additional playback device not to utilize the first route withthe playback device. Yet further, the program logic is executable by theprocessor to enter the low power mode. While the first playback deviceis in the low power mode, the program logic is further executable by theprocessor to periodically receive a message from a master device, wherethe master device is part of the networked media system. Based on themessage, the program logic is further executable by the processor toexit the low power mode.

In yet another aspect, a non-transitory computer-readable storage mediumis provided. The non-transitory computer-readable storage mediumincludes a set of instructions for execution by a processor. The set ofinstructions, when executed, cause a playback device to determine thatthe playback device should enter a low power mode, where the playbackdevice is part of a networked media system. Based on the determination,the set of instructions, when executed, cause the playback device toidentify at least one additional playback device that is part of thenetworked media system, where the playback device is configured tocommunicate with the at least one additional playback device via (i) afirst route, and (ii) a second route. Further, the set of instructions,when executed, cause the playback device to inform the at least oneadditional playback device not to utilize the first route with theplayback device. Further, the set of instructions, when executed, causethe playback device to enter the low power mode. While the firstplayback device is in the low power mode, the set of instructions, whenexecuted, cause the playback device to periodically receive a messagefrom a master device, where the master device is part of the networkedmedia system. Based on the message, the set of instructions, whenexecuted, cause the playback device to exit the low power mode.

Additionally, references herein to “embodiment” means that a particularfeature, structure, or characteristic described in connection with theembodiment can be included in at least one example embodiment of theinvention. The appearances of this phrase in various places in thespecification are not necessarily all referring to the same embodiment,nor are separate or alternative embodiments mutually exclusive of otherembodiments. As such, the embodiments described herein, explicitly andimplicitly understood by one skilled in the art, can be combined withother embodiments.

The specification is presented largely in terms of illustrativeenvironments, systems, procedures, steps, logic blocks, processing, andother symbolic representations that directly or indirectly resemble theoperations of data processing devices coupled to networks. These processdescriptions and representations are typically used by those skilled inthe art to most effectively convey the substance of their work to othersskilled in the art. Numerous specific details are set forth to provide athorough understanding of the present disclosure. However, it isunderstood to those skilled in the art that certain embodiments of thepresent disclosure can be practiced without certain, specific details.In other instances, well known methods, procedures, components, andcircuitry have not been described in detail to avoid unnecessarilyobscuring aspects of the embodiments. Accordingly, the scope of thepresent disclosure is defined by the appended claims rather than theforgoing description of embodiments.

When any of the appended claims are read to cover a purely softwareand/or firmware implementation, at least one of the elements in at leastone example is hereby expressly defined to include a tangible mediumsuch as a memory, DVD, CD, Blu-ray, and so on, storing the softwareand/or firmware.

I claim:
 1. A first playback device of a networked media system, thefirst playback device comprising: a battery configured to power thefirst playback device; one or more processors; and tangible,non-transitory computer-readable memory having stored thereoninstructions executable by the one or more processors, wherein theinstructions, when executed, cause the first playback device to performfunctions comprising: while operating in a normal power mode,maintaining information in a network table, wherein the informationcomprises (i) first information associated with a second playback deviceof the networked media system and (ii) second information associatedwith a third playback device of the networked media system; determiningthat the first playback device is to enter a low power mode to draw lesspower from the battery relative to the normal power mode; responsive tothe determination, foregoing maintaining of the second information inthe network table; after foregoing the maintaining the of the secondinformation, determining that the first playback device is to return tonormal power mode; and in response to determining that the firstplayback device is to return to normal power mode, synchronizing withthe second playback device based at least in part on the firstinformation for playback of audio content.
 2. The first playback deviceof claim 1, wherein the functions further comprise: probing for otherplayback devices in the networked media system while operating in thenormal power mode; and ceasing to probe for other playback devices inthe networked media system in response to determining that the firstplayback device is to enter the low power mode.
 3. The first playbackdevice of claim 1, wherein the functions further comprise ceasing tosubsequently update the second information in response to determiningthat the first playback device is to enter the low power mode.
 4. Thefirst playback device of claim 1, wherein the functions further compriseupdating the second information in response to determining that thefirst playback device is to return to the normal power mode.
 5. Thefirst playback device of claim 1, wherein the second informationcomprises a network address of the third playback device in thenetworked media system.
 6. The first playback device of claim 1, whereinthe second information further comprises an identification of a routingprotocol for communicating with the third playback device over thenetworked media system.
 7. The first playback device of claim 1, whereindetermining that the first playback device is to enter the low powermode comprises determining that a battery power level of the firstplayback device is below a predetermined threshold value.
 8. Anon-transitory computer readable medium having stored thereoninstructions executable by a first playback device of a networked mediasystem to perform functions comprising: while operating in a normalpower mode, maintaining information in a network table, wherein theinformation comprises (i) first information associated with a secondplayback device of the networked media system and (ii) secondinformation associated with a third playback device of the networkedmedia system; determining that the first playback device is to enter alow power mode to draw less power from a battery of the first playbackdevice relative to the normal power mode; responsive to thedetermination, foregoing maintaining of the second information in thenetwork table; after foregoing the maintaining the of the secondinformation, determining that the first playback device is to return tonormal power mode; and in response to determining that the firstplayback device is to return to normal power mode, synchronizing withthe second playback device based at least in part on the firstinformation for playback of audio content.
 9. The non-transitorycomputer readable medium of claim 8, wherein the functions furthercomprise: probing for other playback devices in the networked mediasystem while operating in the normal power mode; and ceasing to probefor other playback devices in the networked media system in response todetermining that the first playback device is to enter the low powermode.
 10. The non-transitory computer readable medium of claim 8,wherein the functions further comprise ceasing to subsequently updatethe second information in response to determining that the firstplayback device is to enter the low power mode.
 11. The non-transitorycomputer readable medium of claim 8, wherein the functions furthercomprise updating the second information in response to determining thatthe first playback device is to return to the normal power mode.
 12. Thenon-transitory computer readable medium of claim 8, wherein the secondinformation comprises a network address of the third playback device inthe networked media system.
 13. The non-transitory computer readablemedium of claim 8, wherein the second information further comprises anidentification of a routing protocol for communicating with the thirdplayback device over the networked media system.
 14. The non-transitorycomputer readable medium of claim 8, wherein determining that the firstplayback device is to enter the low power mode comprises determiningthat a battery power level of the first playback device is below apredetermined threshold value.
 15. A method comprising: while operatingin a normal power mode, maintaining, via a first playback device of anetworked media system, information in a network table, wherein theinformation comprises (i) first information associated with a secondplayback device of the networked media system and (ii) secondinformation associated with a third playback device of the networkedmedia system; determining that the first playback device is to enter alow power mode to draw less power from a battery of the first playbackdevice relative to the normal power mode; responsive to thedetermination, foregoing maintaining of the second information in thenetwork table; after foregoing the maintaining the of the secondinformation, determining that the first playback device is to return tonormal power mode; and in response to determining that the firstplayback device is to return to normal power mode, synchronizing withthe second playback device based at least in part on the firstinformation for playback of audio content.
 16. The method of claim 15,further comprising: probing for other playback devices in the networkedmedia system while operating in the normal power mode; and ceasing toprobe for other playback devices in the networked media system inresponse to determining that the first playback device is to enter thelow power mode.
 17. The method of claim 15, further comprising ceasingto subsequently update the second information in response to determiningthat the first playback device is to enter the low power mode.
 18. Themethod of claim 15, further comprising updating the second informationin response to determining that the first playback device is to returnto the normal power mode.
 19. The method of claim 15, wherein the secondinformation comprises a network address of the third playback device inthe networked media system.
 20. The method of claim 15, wherein thesecond information further comprises an identification of a routingprotocol for communicating with the third playback device over thenetworked media system.